Hey!



I have a W2K12 R2 Server with SCVMM 2012 R2 CU4 and enabled WDS-Role.

The Server ist already registered as a PXE-Server within SCVMM.

When I start a Bare-Metal-Deplyoment, it fails during DeepDiscovery, because it's not booting into the Bootimage using PXE.

I had to set DHCP-Options 66 (SCVMM-IP) and 67 (boot\x64\wdsnbp.com).

The VMM OSD Provider is installed. Below is the output of wdsutil /get-server /show:config I have also checked the path (D:\RemoteInstall\DCMgr\bin\OSDPxeProvider.dll) for the .dll

WDS PXE Providers:
     Name: VMMOSDProvider
     Path: D:\RemoteInstall\DCMgr\bin\OSDPxeProvider.dll
     Order: 1
     Critical: Yes

     Name: WDSDCPXE
     Path: C:\Windows\system32\wdsdcpxe.dll
     Order: 2
     Critical: No

Within WDS PXE is configured to respond only to knwon Clients (or not to any)

In the WDS-EventLog I Receive the following error:
The following client attempted to boot from PXE but was ignored because it is not recognized: 

Hardware Address: 40-F2-E9-C3-71-74
IP: 192.168.222.5
Device ID: {2740D0D9-885B-11E4-AF74-40F2E9C37170}
ClientArchitecture: 1
Prestaged: false

The Device GUIDs are matching between VMM and the Device.

Do you havbe any further Ideas?

Kind Regards
jojo

Hi Sir,

As the title you posted , it is VMM bare-metal-deployment .

Please refer to following artiles for VMM bare-metal-deployment :

https://technet.microsoft.com/en-us/library/gg610658.aspx

http://borgamentes.blogspot.in/2013/09/bare-metal-deployment-with-vmm-2012-sp1.html

Hope it is helpful to you .

Best Regards,

Elton Ji

Hey,

thanks for the reply but i know how Bare-Metal-Deployment works, i implemented it  a few times ago. i just have the Problem within one Customer-Environment, that the PXE-Provider seems not working correctly.

Kind Regards

Jojo